How to remove a "Team" that has an associated schedule?

#1

Hello, First time using the PD Community! :grinning:

I’ve been using PD for over a year now and came across an issue when removing a team. The team had an associated schedule that I was not able to remove. I could not delete the schedule as it was being used on another escalation policy. There was a trick on how to move it and of course I did not record the steps. So, here I am with the same issue and my live chat is not available so I thought to add it here as others many know the steps and this may be handy for others to use as well, if a solution is added.

1 Like
#2

Hi Dave! We’re happy to have you in the PD Community!

You have the ability to assign a schedule to a team at its creation but it can not be removed directly afterwards.

To work around this, you can do the following:

  • Create a new (temporary) escalation policy and assign it to the team you want to unlink the pairing from
  • Add the schedule(s) in question to the same escalation policy
  • Save the escalation policy
  • Edit the escalation policy
  • Select the X next to the team to unlink the team associated with the newly create escalation policy
  • Save the escalation policy (with all of the schedules still assigned to it)
  • Edit & Delete the escalation policy

Once the steps are complete, the team’s association with the schedule should be removed. Hope this helps!

4 Likes
#3

Hi Dave,

I am interested to hear that there are other customers that are having issues with the live chat button not working in their environment - is this still the case with you?

We have been wrestling with this for over 3 months now and have a support ticket open with PagerDuty - the problem is compounded by the fact that apparently the chat functionality is supplied by a 3rd Party (Olark). We think we’re finally getting somewhere, after intensive investigation at our end … it looks like there are calls to various analytics and web ad URLs which our company proxy is not allowing. We’ve fed this back to support and are waiting a response from the Engineering team.

Chris

1 Like
#4

Manual works for it is not good! We can’t destroy the team that has an associated schedule with terraform. Which is awful!

1 Like
#5

Hello Nadine Javier,

Is there any reason for such inconvenience? Are there any plans to fix it assuming how old the issue? I just faced the same problem twice and it takes a lot of time to use that workaround not saying that it takes a lot to explain any develop who face the same issue in our team.

Thanks,
Yuri.

2 Likes
#6

@Inactive-Member-79116629

This can’t be the ultimate solution 2 years later. Please tell me there’s a better way to remove a team. Seriously, there should be an interactive (X) to remove a schedule or escalation policy from it’s linking to a team.

1 Like
#7

mid-2022 and this is still the solution. Pagerduty team @Inactive-Member-79116629 , when will this be fixed?

1 Like
#8

Any update on this issue? This is an unintuitive workflow.

2 Likes
#9

We have our setup in Terraform, and got the error message "Error: DELETE API call to https://api.pagerduty.com/teams/PV2471Q failed 400 Bad Request. Code: 6006, Errors: [Cannot delete team with existing Schedules association(s)], Message: Team has existing associations”

This is a horrible workaround and very tricky to pull off via Terraform.

1 Like
#10

I join to previous requests.
The suggested workaround is horrible, please supply another method to remove a team from an associated schedule.

2 Likes
#11

I agree with my fellow community members, just came across this issue in my own instance and cannot believe that this cannot be simplified.

2 Likes
#12

I am hitting this issue quite often.

Trying to keep my PD config clean and remove unused teams, I hit this every single time I need to remove a team.

2 Likes
#13

@Inactive-Member-79116629 are there any plan to improve this and avoid this workaround ?
we are in 2023 most of our workflow are automated and using terraform to manage pager duty at scale. How do we suppose to create/destroy pizza teams if we have such a limitation ?

1 Like
#14

This is not an acceptable solution. It should be much easier than this. How can I raise a feature request to address this?

#15

Hi Folks!
Some new features are being rolled out in batches to customers regarding schedules.
These features are currently rolling out to all customers. I’ll leave this thread open a few more days for folks, but then I’m going to lock it and if folks have questions about the new features they can start a new thread instead of dragging folks through all the history of the obsolete features.

All customers can now easily remove a schedule’s non-inherited team associations directly in the UI .

Currently this can be done by admin users (and account owners). Historically schedule-team association removal has required a convoluted set of steps; those steps will continue to be required (for now) for users with lower roles (e.g., Manager ) to disassociate a team from a schedule. Teams that are associated to a schedule via an escalation policy (i.e., schedules that inherit a team association from an escalation policy on which the schedules are included) will appear as greyed out, as they are not eligible for this new removal method and must be removed from the escalation policy.

Updated
Here’s the video for folks!

2 Likes
#16